fix: retune defensive precision followups - #83
Merged
Conversation
alxxjohn
added a commit
that referenced
this pull request
Jul 28, 2026
🤖 I have created a release *beep* *boop* --- ## [1.3.6](v1.3.5...v1.3.6) (2026-07-28) ### Bug Fixes * report retry-mitigated sequence debt ([8c7a6d5](8c7a6d5)) * retune defensive precision followups ([a9367ae](a9367ae)) * retune defensive precision followups ([#83](#83)) ([ef6111a](ef6111a)) * treat allocators as command style ([4d7dfa9](4d7dfa9)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR retunes the next batch of CodeGuard precision false positives from TypeScript/JavaScript API and integration code. The goal is to keep the production-readiness checks useful while avoiding noisy findings for patterns that are already bounded, typed, or intentionally surfaced to callers.
What changed
Retuned
defensive.integer-overflow.count + 1external ID allocation as numeric overflow.Refined
defensive.sequence-collision-risk.count + 1external ID allocation is now reported under sequence-collision risk instead of integer overflow.P2002/ unique-collision retry is treated as mitigation, not full resolution.Retuned
defensive.bounds-assumption.fieldMap[name]andprocess.env[name].Retuned
defensive.missing-resource-limit.take.formData()content-length helper guards.Retuned
function.inconsistent-return-contract.T | null.exists()true/false contracts.return falseso it is no longer treated as an empty return.Retuned
error.partial-failure-hidden.catch/continuepaths covered.Updated user-facing metadata.
docs/checks.mdfor the retry-mitigated sequence-debt behavior.Tests
takeand pre-formData()content-length helper guards.Validation
go test ./tests/checks -count=1go test ./...golangci-lint runmake codeguard-ci